Add ManagedServerSecurityAlertPolicy and ManagedDatabaseSecurityAlert…#4521
Add ManagedServerSecurityAlertPolicy and ManagedDatabaseSecurityAlert…#4521praries880 merged 3 commits intoAzure:masterfrom talhers:master
Conversation
|
If you're a MSFT employee, click this link |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-nodeA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
|
Can one of the admins verify this patch? |
|
@talhers Have the new APIs been through an API review? |
These APIs are similar to the regular server and database APIs: The difference is that they apply to managed instance and managed database (except for that they are identical) |
ravbhatnagar
left a comment
There was a problem hiding this comment.
@talhers - some comments. please take a look.
| "application/json" | ||
| ], | ||
| "paths": { | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/managedInstances/{managedInstanceName}/databases/{databaseName}/securityAlertPolicies/{securityAlertPolicyName}": { |
There was a problem hiding this comment.
LIST api to get all securityAlertPolicies for a database missing.
There was a problem hiding this comment.
We will open a work item for this
| "produces": [ | ||
| "application/json" | ||
| ], | ||
| "paths": { |
There was a problem hiding this comment.
Also, it may be helpful to have a PATCH APi for this. For example to update the state of a policy, doing a PUT may be an overkill. PATCH will be much more convenient.
There was a problem hiding this comment.
After thinking about it we don't think that a patch is needed in our customer scenarios
| "description": "Specifies the blob storage endpoint (e.g. https://MyAccount.blob.core.windows.net). This blob storage will hold all Threat Detection audit logs.", | ||
| "type": "string" | ||
| }, | ||
| "storageAccountAccessKey": { |
There was a problem hiding this comment.
should not be returned in the response of a Get or PUT. A better model may be to fetch it on behalf of the user using s2S auth.
There was a problem hiding this comment.
We will open a work item for this
| "produces": [ | ||
| "application/json" | ||
| ], | ||
| "paths": { |
There was a problem hiding this comment.
same comments as above.
There was a problem hiding this comment.
We will open a work item for this
|
We will open work items on the comments above and fix them in our next API version. |
|
Couple of pending issues Tracked here #4910 |
Azure#4521) * Add ManagedServerSecurityAlertPolicy and ManagedDatabaseSecurityAlertPolicies * fix incompatible values in swagger * Fix ManagedDatabaseSecurityAlertCreateMin example file
…Policies
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist: